-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
feat: Add typescript support #595
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
feat: Add typescript support #595
Conversation
I will reformat the title to use the proper commit message syntax. |
🚀 Thanks for opening this pull request! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
- Modify package.json scripts and dependencies - Update index.ts for TypeScript compatibility
ddcd572
to
fc7e68a
Compare
0ff84ec
to
4a1ae28
Compare
9524cf2
to
fd27b5b
Compare
const mountPath = process.env.PARSE_MOUNT || '/parse'; | ||
const server = new ParseServer(config); | ||
|
||
server.start().then(async () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use top level await here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have to convert the project to a module by adding type:module in package.json and incrementing the module and target in tsconfig making it not the same as Parse and Parse Server configs.
Should I change it in the tsconfig?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, it's not necessary, if you feel like doing it, then I'll wait with merging, otherwise let me know and we merge as is.
Closes #561